Methods, systems, and media for interpreting queries

ABSTRACT

Mechanisms for interpreting queries are provided. In some implementations, a method for interpreting queries is provided, comprising: receiving a search query in a search domain; determining search terms based on the search query; determining, for each of the search terms, whether a search term corresponds to an entity name, wherein the entity name is derived from metadata associated with the search domain; in response to determining that entity names correspond to a portion of the search terms, determining an entity type and an entity score associated with each of the corresponding entity names; determining a remaining portion of the entity names by removing at least one of the matching entity names based on the entity score and contextual information in the search query; and performing a search in the search domain with the remaining portion of entity names, wherein each entity name in the remaining portion of entity names is searched corresponding to the associated entity type.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/677,020, filed Nov. 14, 2012, which is hereby incorporated byreference herein in its entirety.

TECHNICAL FIELD

Methods, systems, and media for interpreting queries are provided. Moreparticularly, the disclosed subject matter relates to interpretingqueries based on entity information.

BACKGROUND

There is an overwhelming volume of content that is available to theaverage consumer. For example, with respect to media content, there aremany applications that a consumer can use on a television or set-top boxthat allow the consumer to consume media content from various sources(e.g., media content that is delivered linearly from a multichannelvideo programming distributor, video-on-demand content that is providedby a multichannel video programming distributor, personal media contentthat is acquired by the consumer, recorded content that is stored on adigital video recorder or any other suitable storage device, and/oron-demand content that is provided from over-the-top providers).

As the number of sources and the volume of content continue to increase,consumers are increasingly reliant on search engines, where a consumercan formulate a search query that includes search constraints thatidentify what information is being sought. Search engines have beendeveloped that receive such search queries and return search resultsresponsive to the search query. Some search engines, however, provide abroad set of search results without having an understanding of thesearch query. For example, in response to providing the search query“action movie with tom cruise,” these search engines can provideirrelevant search results like “Last Action Hero” and “Tom and Jerry”simply because a portion of the search query is included in the title ofthe pieces of content.

Accordingly, gaining an understanding of the search query can producemore meaningful search results.

SUMMARY

In accordance with various implementations of the disclosed subjectmatter, mechanisms for interpreting queries are provided.

In accordance with some implementations of the disclosed subject matter,a method for interpreting queries is provided, the method comprising:receiving, using a hardware processor, a search query in a searchdomain; determining, using the hardware processor, a plurality of searchterms based on the received search query; determining, using thehardware processor, for each of the plurality of search terms, whether asearch term of the plurality of search terms corresponds to an entityname, wherein the entity name is derived from metadata associated withthe search domain; in response to determining that a plurality of entitynames corresponds to at least a portion of the plurality of searchterms, determining, using the hardware processor, an entity type and anentity score associated with each of the plurality of correspondingentity names; determining, using the hardware processor, a remainingportion of the plurality of entity names by removing at least one of theplurality of matching entity names based at least in part on the entityscore and contextual information in the received search query; andperforming, using the hardware processor, a search in the search domainwith the remaining portion of the plurality of entity names, whereineach entity name in the remaining portion of the plurality of entitynames is searched corresponding to the associated entity type.

In accordance with some implementations of the disclosed subject matter,a system for interpreting queries is provided. The system comprising: astorage device for storing entity information, wherein the entityinformation is derived from metadata associated with a search domain;and a processor that is configured to: receive a search query in thesearch domain; determine a plurality of search terms based on thereceived search query; determine, for each of the plurality of searchterms, whether a search term of the plurality of search termscorresponds to an entity name; in response to determining that aplurality of entity names corresponds to at least a portion of theplurality of search terms, determine an entity type and an entity scoreassociated with each of the plurality of corresponding entity names;determine a remaining portion of the plurality of entity names byremoving at least one of the plurality of matching entity names based atleast in part on the entity score and contextual information in thereceived search query; and perform a search in the search domain withthe remaining portion of the plurality of entity names, wherein eachentity name in the remaining portion of the plurality of entity names issearched corresponding to the associated entity type.

In accordance with some implementations of the disclosed subject matter,a computer-readable medium containing computer-executable instructionsthat, when executed by a processor, cause the processor to perform amethod for interpreting queries, is provided. The method comprises:receiving a search query in a search domain; determining a plurality ofsearch terms based on the received search query; determining, for eachof the plurality of search terms, whether a search term of the pluralityof search terms corresponds to an entity name, wherein the entity nameis derived from metadata associated with the search domain; in responseto determining that a plurality of entity names corresponds to at leasta portion of the plurality of search terms, determining an entity typeand an entity score associated with each of the plurality ofcorresponding entity names; determining a remaining portion of theplurality of entity names by removing at least one of the plurality ofmatching entity names based at least in part on the entity score andcontextual information in the received search query; and performing asearch in the search domain with the remaining portion of the pluralityof entity names, wherein each entity name in the remaining portion ofthe plurality of entity names is searched corresponding to theassociated entity type.

In accordance with some implementations of the disclosed subject matter,a method for interpreting queries is provided, the method comprising:receiving, using a hardware processor, a voice query in a search domain;determining, using the hardware processor, a plurality of voicerecognition terms based on the received voice query; determining, usingthe hardware processor, for each of the plurality of voice recognitionterms, whether at least a portion of a voice recognition termcorresponds to an entity name, wherein the entity name is derived frommetadata associated with the search domain and wherein an entity scoreis associated with the entity name; determining, using the hardwareprocessor, a feasibility score for each of the plurality of voicerecognition terms based on the entity score; ranking the plurality ofvoice recognition terms based on the determined feasibility score; andselecting, using the hardware processor, one of the plurality of rankedvoice recognition terms for executing the voice query in the searchdomain.

In accordance with some implementations of the disclosed subject matter,a system for interpreting queries is provided. The system comprising: astorage device for storing entity information, wherein the entityinformation is derived from metadata associated with a search domain;and a processor that is configured to: receive a voice query in a searchdomain; determine a plurality of voice recognition terms based on thereceived voice query; determine, for each of the plurality of voicerecognition terms, whether at least a portion of a voice recognitionterm corresponds to an entity name, wherein the entity name is derivedfrom metadata associated with the search domain and wherein an entityscore is associated with the entity name; determine a feasibility scorefor each of the plurality of voice recognition terms based on the entityscore; rank the plurality of voice recognition terms based on thedetermined feasibility score; and select one of the plurality of rankedvoice recognition terms for executing the voice query in the searchdomain.

In accordance with some implementations of the disclosed subject matter,a computer-readable medium containing computer-executable instructionsthat, when executed by a processor, cause the processor to perform amethod for interpreting queries, is provided. The method comprises:receiving a voice query in a search domain; determining a plurality ofvoice recognition terms based on the received voice query; determining,for each of the plurality of voice recognition terms, whether at least aportion of a voice recognition term corresponds to an entity name,wherein the entity name is derived from metadata associated with thesearch domain and wherein an entity score is associated with the entityname; determining a feasibility score for each of the plurality of voicerecognition terms based on the entity score; ranking the plurality ofvoice recognition terms based on the determined feasibility score; andselecting one of the plurality of ranked voice recognition terms forexecuting the voice query in the search domain.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, features, and advantages of the disclosed subjectmatter can be more fully appreciated with reference to the followingdetailed description of the disclosed subject matter when considered inconnection with the following drawing, in which like reference numeralsidentify like elements.

FIG. 1 is a flowchart of an illustrative process for interpreting asearch query based on entity information and providing search resultsresponsive to the search query in accordance with some implementationsof the disclosed subject matter.

FIG. 2 is a flowchart of an illustrative process for generating entityinformation from metadata associated with a search domain in accordancewith some implementations of the disclosed subject matter.

FIG. 3 is an illustrative example of an entity table that includesentity names extracted from metadata associated with a search domain andtheir associated entity types and entity scores in accordance with someimplementations of the disclosed subject matter.

FIG. 4 is an illustrative screen of a search interface for receivingsearch queries in accordance with some implementations of the disclosedsubject matter.

FIG. 5 is an illustrative example of entity results obtained from theentity table of FIG. 3 in response to search terms extracted from asearch query in accordance with some implementations of the disclosedsubject matter.

FIG. 6 is an illustrative example of interpreted entity results based onentity scores and contextual information in accordance with someimplementations of the disclosed subject matter.

FIG. 7 is an illustrative screen of a search interface that providessearch results responsive to a search query in accordance with someimplementations of the disclosed subject matter.

FIG. 8 is a flowchart of an illustrative process for interpreting avoice query based on entity information and feasibility scores inaccordance with some implementations of the disclosed subject matter.

FIG. 9 is an illustrative example of an interpreted voice queryincluding voice recognition terms based on the received voice query,matching entities, and feasibility scores in accordance with someimplementations of the disclosed subject matter.

FIG. 10 is a diagram of an illustrative system suitable implementationof the query interpretation application in accordance with someimplementations of the disclosed subject matter.

FIG. 11 is a diagram of an illustrative computing device and server asprovided, for example, in FIG. 10 in accordance with someimplementations of the disclosed subject matter.

DETAILED DESCRIPTION

Methods, systems, and media for interpreting queries are provided.

In accordance with some implementations of the disclosed subject matter,mechanisms for interpreting queries, such as search queries and voicequeries, are provided. In response to receiving a query in a searchdomain, the query can be interpreted by determining search terms basedon the received query and searching for entity information thatcorresponds to the search terms. For example, in response to receivingthe query “action movie with tom cruise,” the query can be segmented toobtain initial search terms that include “action movie with tom cruise,”“action movie with tom,” “movie with tom cruise,” “action movie,” “moviewith tom,” “with tom cruise,” “movie with,” “with tom,” “tom cruise,”“action,” “movie,” “with,” “tom,” “cruise,” etc. Using entityinformation, it can be determined whether one or more of these searchterms corresponds to entity information. For example, it can bedetermined that the terms “action,” “movie,” “tom cruise,” “tom,” and“the cruise” correspond to entity names located in a table of entityinformation.

In some implementations, entity information can be identified frommetadata that is associated with a search domain. In a more particularimplementation, a table that includes entity information can be createdby retrieving metadata from one or more suitable sources and identifyingentities from the retrieved metadata. In a media search domain, metadataassociated with television programs and movies can be retrieved and theidentified entities can include television program titles, movie titles,actor names, character names, director names, genres or categoryinformation, etc. Each of these entities can have an associated entitytype and an associated entity score.

It should be noted that, in some implementations, the associated entityscore can be based on the popularity of the entity within the particularsearch domain. This can, for example, allow the mechanisms to resolveconflicts between entities having the same or similar entity names. Forexample, if a television program having the title “house” is determinedto be more popular than a movie having the title “house,” the televisionprogram can receive a higher entity score than the movie. In anotherexample, in some cases, the search term “house” having the entity typecorresponding to a movie title and having a lower entity score can beremoved from the set of initial search terms (e.g., a higher entityscore can be used to indicate a more relevant or more frequentlysearched result).

It should also be noted that, in some implementations, the associatedentity score can be an aggregate entity score. For example, an entityscore associated with the actor “tom cruise” can be the average of theentity scores calculated for each television program, movie, and/orother suitable media content associated with “tom cruise.” In anotherexample, an entity score associated with a channel identifier “AAA” canbe the average of the entity scores for each television program providedby that channel.

Upon determining which search terms correspond with entities, some ofthe search terms (e.g., unlikely search terms) can be removed based onentity scores associated with the entities and/or contextual informationderived from the search query. For example, the entity “house” havingthe entity type MOVIE may be removed from the search terms when thehigher scoring entity “house” having the entity type SERIES is alsopresent. In another example, overlapping entities can be removed fromthe search terms, such as the search term “tom” when the search term“tom cruise” includes the term “tom.” In yet another example, a searchterm can be removed based on context within the received search query.In a more particular example, the term “2012” from the search query“action movie 2012” is unlikely to be a movie title having the entitytype MOVIE because of its positioning within the search query andbecause of the other terms within the search query. Based on contextwithin the search query, the term “2012” has a greater likelihood ofhaving an entity type of RELEASE DATE or AIRING DATE. If the searchquery included the term “2012” alone, the contextual information canindicate that the term “2012” may have a greater likelihood of being amovie title and having the entity type MOVIE.

Upon removing unlikely search terms, the remaining search terms can beused to perform a search in the search domain. Referring back to theabove-mentioned search query of “action movie with tom cruise,” if theremaining search terms are “action” having the entity type GENRE,“movie” as a result type (e.g., entity type CORPUS_TYPE_MOVIE), and “tomcruise” having the entity type ACTOR_NAME, a search in the media searchdomain can be performed by providing “action” in a genre search field,“tom cruise” in an actor name search field, and “movie” in a result typefield. The search results responsive to these remaining search terms canthen, for example, be provided to a user of the media playback device.

In some implementations, the query interpretation mechanisms can be alsobe used to interpret voice queries or voice commands. In response toreceiving a voice query, the mechanisms can use entity information toselect from voice recognition results based on entity scores andfeasibility scores. For example, in response to receiving a voice query,the voice query can be interpreted by determining voice recognitionresults and searching for entity information that corresponds to thevoice recognition results. A feasibility score based on entity scorescan be calculated for each of the voice recognition results and thevoice recognition results can be ranked based on the calculatedfeasibility score. A feasible voice recognition result from the set ofvoice recognition results can then be selected from the voicerecognition results. In response to selecting a feasible voicerecognition result, the mechanisms can cause a suitable command in amedia playback device to be performed. For example, in responsereceiving a voice query of “watch CNN,” the mechanisms can interpret thevoice query and cause the media playback device to tune to the channelassociated with the CNN channel identifier (e.g., as opposed tolaunching the website www.cnn.com).

Although the implementations described herein generally relate tointerpreting queries for media content, such as television programs,movies, and video clips, this is merely illustrative. For example, thesequery interpretation mechanisms can be implemented in a product searchdomain, where the entity information is identified from structuredproduct metadata (e.g., product name, manufacturer name, price, productcategory, product rating, merchant name, etc.). In another example,these query interpretation mechanisms can be implemented in a musicsearch domain, where the entity information is identified fromstructured music metadata (e.g., song title, artist name, album title,release year, music genre, audio format, etc.). In yet another example,these query interpretation mechanisms can be implemented in a books andliterature search domain, where the entity information is identifiedfrom structured book data (e.g., book title, author name, publishername, publication date, number of pages, book genre, book format, etc.).Accordingly, the query interpretation mechanisms can be used in anysuitable search domain for providing relevant search results in thesearch domain.

Turning to FIG. 1, FIG. 1 is a flow chart of an illustrative process 100for providing a query interpretation application, where a search queryis interpreted based on entity information, in accordance with someimplementations of the disclosed subject matter.

Process 100 can begin by receiving a search query at 110. For example,using a media playback device (e.g., a television device, a set-top box,a tablet computing device), a search interface can be presented to auser of the media playback device for inputting search queries. Anexample of a search query can be “action movie with tom cruise.” Asdescribed in connection with FIG. 8, the query interpretationapplication can also receive other suitable queries, such as voicequeries that are captured by a media playback device having audio inputcapabilities. The received search query can be transmitted to the queryinterpretation application for processing.

At 120, the query interpretation application can determine one or moresearch terms based on the received search query. For example, inresponse to receiving the search query “action movie with tom cruise,”the query interpretation application can segment the received searchquery to obtain search terms, such as “action movie with tom cruise,”“action movie with tom,” “movie with tom cruise,” “action movie with,”“movie with tom,” “with tom cruise,” “action movie,” “movie with,” “withtom,” “tom cruise,” “action,” “movie,” “with,” “tom,” and “cruise.”

At 130, the query interpretation application can determine whether oneor more of the search terms correspond to entity information. Forexample, the query interpretation application can access an entity tablethat includes entity names derived from media content-related metadataand determine whether one or more of the search terms is associated withan entity name in the entity table. In a more particular example, thequery interpretation application can perform a table lookup operation inthe entity table to determine which search terms are associated withentity names in the entity table. In another more particular example,the query interpretation application can transmit a query to a datasource including the entity table, where the query requests anindication of which search terms match entity names in the entity table.

Turning to FIG. 2, FIG. 2 is a flow chart of an illustrative process 200for generating entity information from metadata associated with a searchdomain in accordance with some implementations of the disclosed subjectmatter.

In some implementations, process 200 can begin by determining the searchdomain at 210. For example, as described above, the search domain can bea media content domain that includes television programs, movies, videoclips, and other media content. The query interpretation application candetermine that the search query is received from a media playback deviceand, in response, can restrict the search query to a media contentdomain. As also described above, the query interpretation applicationcan be implemented with any suitable search domain, such as a books andliterature search domain, a music search domain, a product searchdomain, etc.

At 220, in response to determining the search domain, the queryinterpretation application can access one or more suitable sources formetadata associated with the search domain. For example, in a mediasearch domain on a media playback device, the query interpretationapplication can retrieve metadata associated with the media searchdomain from multiple sources, such as a media content source, a mediadata source, and/or any other suitable database containing data relatingto media content available for presentation to the user. In anotherexample, the query interpretation application can transmit a query tothe database or any other suitable source for metadata associated withthe media search domain.

In some implementations, the query interpretation application canprovide the user with an opportunity to select from available databasesor sources. For example, in a media search domain, the queryinterpretation application can prompt the user to select from a databaseassociated with a content provider, an online database of informationrelating to movies and television programs, etc.

At 230, the query interpretation application can extract entity namesbased on metadata retrieved from one or more sources. For example, in amedia search domain, the query interpretation application can receivemetadata associated with various television programs and movies and usethe received metadata to extract entity names that include televisionseries titles, movie titles, actor names, producer names, fictionalcharacter names, genre or category information, etc. In a product searchdomain, the query interpretation application can extract product names,manufacturer names, prices, product categories, product ratings, andmerchant names based on the metadata retrieved from one or more sources.In a music search domain, the query interpretation application canextract song titles, artist names, album titles, release years, musicgenres, and audio formats from the retrieved metadata. In a book searchdomain, the query interpretation application can extract book titles,author names, publisher names, publication dates, number of pages, bookgenres, and book formats from the retrieved metadata.

It should be noted that each entity name has an associated entity type,such as a television series type, a movie title type, an actor nametype, a genre type, etc. For example, the entity name “house” can havean entity type corresponding to a television series title (e.g., aSERIES entity type). In another example, the entity name “house” canhave multiple entity types—e.g., an entity name “house” can have aSERIES entity type indicating that it is the title of a televisionseries and a MOVIE entity type indicating that it is also the title of amovie.

It should also be noted that each entity name can also have anassociated entity score. In some implementations, the entity score canbe calculated and/or assigned based on the popularity of the entity namewithin the search domain at 240. For example, the query interpretationapplication can calculate a popularity score for an entity name based onany suitable number of criteria. In a more particular example, the queryinterpretation application can calculate a popularity score based onuser ratings for a piece of media content, based on the number of timesthe entity name has been searched, based on the number of times themedia content associated with the entity name has been accessed, and/orany other suitable criteria.

In some implementations, the query interpretation application cancalculate an entity score, where the entity score is a combination ofentity scores or an aggregate entity score. For example, the entityscore for the entity name “tom cruise” can be an average of the entityscores corresponding to each piece of media content associated with theentity name. In a more particular example, the query interpretationapplication can calculate an entity score for an entity name associatedwith a movie that includes the actor “tom cruise” and can propagate thatscore to other entity names (e.g., the entity name “tom cruise,” theentity name associated with the producer of the movie, etc.). In thisexample, the entity score for the entity name “tom cruise” can be anaverage score of the propagated entity scores associated with the moviesin which “tom cruise” is an actor. In another example, the entity scoreassociated with a television channel can be an average of the propagatedentity scores associated with the television programs provided by thattelevision channel (e.g., the entity score for the entity name “ChannelA” can be the average of the entity scores associated with “Program A”through “Program Z” provided by “Channel A”).

Additionally or alternatively, the query interpretation application canassign any suitable weight to each of the entity scores associated withthe media content. For example, the query interpretation application canassign weights to each entity score based on the release date of themedia content. In this example, the entity score for recent movies thatinclude the actor “tom cruise” can have a greater influence on theaggregate entity score than past movies that include the actor.

At 250, the query interpretation application can generate an entitytable that includes the extracted entity names and the associated entitytypes and the entity scores. An illustrative example of an entity tablethat includes entity names extracted from metadata associated with asearch domain and their associated entity types and calculated entityscores is shown in FIG. 3. As shown, the entity table includes themultiple entities having the same name (e.g., the entity name “HOUSE”).As also shown, each entity name has a different entity type (e.g., aMOVIE entity type, a SERIES entity type, a CHARACTER entity type, and anACTOR entity type) and a different entity score associated with it. Theentity table can, for example, define a vocabulary or a dictionary ofwords or phrases for the search domain such that search terms can berestricted to this vocabulary.

It should be noted that, in some implementations, additional informationfor the entity table can be obtained from various sources (e.g.,marketplace sources, social media sources, searching sources, etc.). Forexample, the query interpretation application can access a click logthat includes feedback information relating to users in the searchdomain. The click log can include an indication of the number of timesusers have inputted search queries that include a particular entityname. The click log can also include an indication of the number oftimes users have selected a particular search result for playback oraccessed a particular piece of media content. In response, the queryinterpretation application can use information from the click log to addentity names and/or update entity scores. For example, in response todetermining that a substantial number of users have queried a televisionprogram or have selected a television program that appears as a searchresult, the query interpretation application can increase the associatedentity score (e.g., indicating greater popularity or greater relevance).

It should also be noted that, in some implementations, users may opt outof data collection in click logs. For example, the query interpretationapplication can access statistical information relating to entities inthe given search domain (e.g., statistical information can indicate thatthe entity “tom cruise” is a more popular search term in the searchdomain than the entity “john doe”). Click log information may not beconnected with user names or other personally identifying information.

In some implementations, the query interpretation application can accessan additional source that includes manually curated entity information.Manually curated entity information can include, for example, commonterms that can be ignored by the application when interpreting queriesand/or entity information that may not be included in the metadatasources. In a more particular example, manually curated entityinformation can include the terms “with,” “the,” “a,” “&,” and “and.”This manually curated entity information can also include an instructionthat the query interpretation application may ignore these terms insearch queries. In another more particular example, manually curatedentity information can include an instruction that the queryinterpretation application may ignore particular characters, such asapostrophe marks and hyphens. In yet another more particular example,manually curated entity information can include popular or common entitynames and other entity information that may not be included in themetadata sources (e.g., from a social media source).

In some implementations, the query interpretation application can updatethe entity table and/or any other suitable entity information. Referringback to FIG. 2, at 260, the query interpretation application candetermine whether a predetermined amount of time has elapsed (e.g.,twelve hours, twenty-four hours, one week, etc.). In response todetermining that a predetermined amount of time has elapsed (e.g.,calculating the age of the entity table), the query interpretationapplication can return to 220, where one or more sources are accessedfor retrieving metadata. The query interpretation application can thengenerate an updated entity table based on the newly retrieved metadata.

Alternatively, the query interpretation application can provide theentity table for use in interpreting search queries at 270. For example,when used with a media playback device, the query interpretationapplication can store the entity table in the media playback device.

Referring back to FIG. 1, the query interpretation application can usethe entity information contained in the entity table to determinewhether the search terms correspond to entity names at 130 and determinethe entity type and the entity score associated with the matching entitynames at 140. As mentioned above and as shown in FIG. 4, the searchquery of “action movie with tom cruise” has been inputted by a user in asearch field 410. In response, the query interpretation application candetermine that the search terms “action,” “movies,” “tom cruise,” “tom,”and “the cruise” derived from the search query correspond to entitynames in the entity table. An illustrative example of the entity resultsobtained from the entity table is shown in FIG. 5. As shown in FIG. 5,the entity name “tom cruise” has an entity type ACTOR and has an entityscore of 5.750. As another example, the entity name “the cruise” has anentity type SERIES and has an entity score of 1.000, while an entityhaving the same entity name “the cruise” has an entity type MOVIE andhas an entity score of 5.000 indicating that it is more popular than thetelevision series.

At 150, the query interpretation application can use this entityinformation to interpret the search query. More particularly, the queryinterpretation application can interpret the entity names based onentity scores and/or contextual information.

In some implementations, the query interpretation application can removea search term based on entity scores. For example, as shown in FIG. 5,the query interpretation application can determine whether to remove thesearch term “the cruise” having a SERIES entity type as the search term“the cruise” having a MOVIE entity type has a larger entity scoreindicating that the movie is more popular than the television series. Asalso shown in FIG. 5, for entities having the same entity name, theentity table can be sorted by entity score. In this example, the queryinterpretation application can determine whether to remove one or moresearch terms having lower entity scores, such as the search term“action” having a MOVIE entity type and a low entity score of 0.345.

It should be noted, however, that the query interpretation applicationcan remove search terms based any suitable criteria. For example, insome implementations, the query interpretation application can remove asearch term based on contextual information from the received searchquery. These are sometimes referred to herein as unlikely entities.

In some implementations, the query interpretation application can removeunlikely entities from a set of entity results by removing overlappingsearch terms. In the example shown in FIG. 5, although the entity tableindicated that matching entities include the term “tom” and the term“tom cruise,” the query interpretation application can remove the term“tom” (and its multiple entity types) as the term “tom cruise” includesthe term “tom.”

In some implementations, the query interpretation application can removeunlikely entities from a set of entity results based on contextualinformation in the received search query. Note that the queryinterpretation application can receive a structured search query andinterpret the structured search query as a sequence of multiple searchconstraints. For example, the query interpretation application caninterpret the term “2012” in a search query “action movie 2012” based onthe other terms included in the received search query. In a moreparticular example, the query interpretation application can determinethat the term “2012” from the search query “action movie 2012” isunlikely to be a movie title having the entity type MOVIE because of itsposition within the search query and because of the other terms withinthe search query (e.g., the term “2012” follows the terms “action” and“movie”). In addition, based on contextual information in the searchquery, the query interpretation application can determine that the term“2012” has a greater likelihood of having an entity type of RELEASE DATEor AIRING DATE. Accordingly, the query interpretation application canremove the entity “2012” that has the entity type corresponding to amovie title from the set of entity results. Alternatively, if the searchquery included the term “2012” by itself, the query interpretationapplication can determine that the term “2012” has a greater likelihoodof being a movie title and having the entity type MOVIE.

It should be noted that any suitable approach can be used for removingunlikely entities from a set of entity results. For example, the queryinterpretation application can remove unlikely entities based on clicklog information or any other suitable user feedback information. Moreparticularly, the query interpretation application can determine thatthe term “tom” is rarely searched by other users and, in response, thequery interpretation application can remove the term “tom” as being anunlikely entity for performing the search command. In another example,the query interpretation application can remove unlikely entities basedon additional information sources, such as social media informationsources. More particularly, the query interpretation application canretrieve social media statistics relating to a social media source anddetermine that, although “tom” is rarely searched by other users in themedia search domain, the term “tom” is gaining popularity on the socialmedia source.

As shown in FIG. 6, upon removing unlikely entities based on entityscores and contextual information, the query interpretation applicationcan obtain a set of interpreted entities. More particularly, FIG. 6shows that the query interpretation application has determined that thereceived search query is interpreted to include the term “action” havingan entity type corresponding to a genre (a GENRE entity type), “movies”having an entity type corresponding to the type of search result (aCORPUS_TYPE_MOVIE entity type), and “tom cruise” having an entity typecorresponding to the name of an actor (an ACTOR entity type).

Referring back to FIG. 1, the query interpretation application canperform a search using the set of interpreted entities at 160. Inconnection with the above-mentioned example, the query interpretationapplication can use the entity types associated with each of theinterpreted entities to apply an entity name into a corresponding searchfield. As described in the example above, the query interpretationapplication can apply the term “action” in a genre search field, theterm “movie” as a search result type, and the term “tom cruise” in anactor or actress search field.

In some implementations, the query interpretation application can formatthe set of interpreted entities into a database query, such as aStructured Query Language (SQL) query. An illustrative SQL querygenerated by the query interpretation application that includes the setof interpreted entities can be represented as follows:

SELECT * from MOVIE where GENRE is “action” AND ACTOR is “tom cruise”

The query interpretation application can transmit the SQL query to adatabase and receive a response from the database.

At 170, the query interpretation application can receive the searchresults and cause the search results responsive to the search query tobe displayed to a user. For example, as shown in FIG. 7, the queryinterpretation application can cause search results 710 to be displayedto a user of a media playback device. More particularly, search results710 can be in the form of images (e.g., media cover art) relating to thesearch results. It should be noted that, in some implementations, anysuitable information relating to the search result can be provided tothe user, such as rating information, price information, formatinformation (e.g., available for download from an over-the-top contentsource, available from a video-on-demand source, etc.), etc.

It should be noted that, in some implementations, the queryinterpretation application can be implemented on a mobile device or atablet computing device, where a search interface for searching throughmedia content can be presented on such a device. In this implementation,the search interface and the search results determined using the queryinterpretation application can be provided to the user on a secondscreen device, such as a mobile device or a tablet computing device,while a search result that is selected by the user on the second screendevice can be retrieved and displayed on a media playback device, suchas a television device.

Although the implementations described herein generally relate toreceiving a search query provided by a user using a user input device(e.g., a remote control, a keyboard, a touchpad, a mobile phone, etc.),this is merely illustrative. Search queries can be received andinterpreted using any suitable approach. For example, in accordance withsome implementations, the query interpretation application can be usedto interpret voice queries or voice commands in a particular searchdomain.

FIG. 8 is a flowchart of an illustrative process for interpreting avoice query based on entity information and feasibility scores inaccordance with some implementations of the disclosed subject matter. Asshown, process 800 can begin by receiving a voice query from a user at810. For example, the query interpretation application can receive thevoice query “tune to CNN” from a user using a media playback devicehaving audio input capabilities (e.g., a microphone). In anotherexample, a microphone or any other suitable audio input device on amobile device can be used receive the voice query from the user and themobile device can transmit the voice query to a media playback devicethat is executing the query interpretation application.

At 820, the query interpretation application can determine voicerecognition terms based on the received voice query.

In some implementations, the query interpretation application candetermine that the first portion of the received voice query (e.g.,“tune”) is likely to correspond to an action command term. For example,the query interpretation application can generate a set of terms fromthe first portion of the received voice query (e.g., “two,” “tune,”“tune in,” “turn,” etc.) and compare the set of terms with entities inan entity table having the entity type associated with action commands(e.g., an ACTION entity type). In another example, the entity table canbe supplemented with manually curated entity information that includesparticular entities having the entity type associated with an actioncommand, such as “watch” (for accessing media content), “tune” (fortuning to a channel), “go to” (for accessing a website), and “launch”(for initiating an application). Using the entity table and entityscores within the entity table, the query interpretation application candetermine which action command term is likely to have been provided inthe voice query.

Additionally or alternatively, the query interpretation application canhave a default action command in response to receiving a voice query.For example, the query interpretation application can parse the firstportion of the received voice query and determine that the portion ofthe voice query does not correspond to an action command. In response toreceiving the voice query “Channel A,” the query interpretationapplication can, without receiving additional input from the user,associated the voice query with a predetermined action command to tuneto “Channel A.” The default action command can be based, for example, onthe search domain (e.g., a media content search domain, where the useris using a media playback device).

In some implementations, the query interpretation application can assigndefault action commands based on the other terms in the voice query. Forexample, in response to determining that the voice query “CNN” relatesto a channel identifier, the query interpretation application can usethe entity type to provide a default action command to tune to thechannel associated with the channel identifier. In another example, inresponse to determining that the voice query “CNN” relates to a website,the query interpretation application can use the entity type (e.g., aWEB_SITE entity type) to provide a default action command to launch aweb browsing application and access a website corresponding to the voicequery “CNN.” In yet another example, in response to determining that thevoice query “CNN” relates to both a channel and a website, the queryinterpretation application can determine the default action commandbased on entity score (e.g., the entity score for the channel “CNN” isgreater than the entity score for the website “CNN” and, thus, thedefault action command is to tune to the channel associated with “CNN”).

Referring back to FIG. 8, in some implementations, the queryinterpretation application can determine voice recognition terms basedon the received voice query. For the remainder of the received voicequery (“CNN”), the query interpretation application can generate one ormore of the following voice recognition terms: “seaman,” “sienen,”“shannon,” “c n n,” “cnn,” “cnm,” and/or “cmn.” At 830, the queryinterpretation application can determine whether the voice recognitionterms correspond to entity information. For example, the queryinterpretation application can access an entity table similar to the oneshown in FIG. 3 and determine whether the terms “sienen,” “shannon,” “cn n,” “cnn,” “cnm,” and/or “cmn” match an entity name located in theentity table (e.g., the entity table of FIG. 3).

Alternatively, instead of determining that the first portion of thereceived voice query corresponds to an action command and generatingvoice recognition terms for the remainder of the voice query, the queryinterpretation application can segment the entire voice query togenerate voice recognition terms, such as “tune,” “tune to sienen,”“tune to cnn,” “to cnn,” “turn to,” etc. Similar to the search terms inFIG. 1, the query interpretation application can determine whether oneor more of the generated voice recognition terms correspond to entitynames in an entity table.

FIG. 9 shows an illustrative example of various voice recognition termsgenerated from a voice query and the selected voice recognition term forexecution in accordance with some implementations of the disclosedsubject matter. As shown, in response to the voice query “watch fringe,”the query interpretation application has determined that the voice querycan include the voice recognition terms “watch free music,” “watchfringe,” “watch friends,” “watch free movies,” “watch french,” and “textfree music.” Using the entity table and/or other entity information,FIG. 9 also shows that the query interpretation application hasdetermined entities corresponding with the voice recognition terms. Forexample, the query interpretation application has determined that thevoice recognition term “watch fringe” (shown in column 910) has thematching entities “watch” (with an ACTION_WATCH entity type) and“fringe” (with a SERIES entity type) (shown in columns 920 and 930). Inanother example, the query interpretation application has determinedthat the entire voice recognition term “watch free movies” matches theentity “watch free movies,” which corresponds to a particular websitefor playing back movie content.

Referring back to FIG. 8, the query interpretation application candetermine a feasibility score for each of the voice recognition terms at840. Using the entity table described above, the feasibility score for avoice recognition term can be based on the matching entity names andtheir associated entity scores. For example, if the voice recognitionterms include the terms “house” and “horse” and it is determined that“house” has a higher entity score (e.g., is more popular) than “horse,”the query interpretation application can calculate a feasibility scorethat is based on the entity score. As such, the term “house” can receivea higher feasibility score than “horse” because of the higher entityscore. This can reflect that the term “house” (having an entity typethat corresponds to a television series) is more likely to be queried byusers than the less popular “horse” (having an entity type thatcorresponds to a television channel).

It should be noted, however, that any suitable rules can be provided fordetermining the feasibility score. For example, in some implementations,the query interpretation application can provide penalty scores orpenalty weights that modify the feasibility score. In a more particularexample, the query interpretation application can provide a penaltyscore when terms within the voice recognition term are not recognized asentities in the entity table. If the terms within the voice recognitionterm are recognized as entities, the query interpretation applicationcan assign a low penalty score or not assign a penalty weight (e.g., a1.0 multiplier). If half of the terms within the voice recognition termare recognized as entities, the query interpretation application canassign a penalty score or penalty weight, such as a 0.5 multiplier. Ifnone of the terms within the voice recognition term are recognized asentities within the entity table, the query interpretation applicationcan assign a high penalty score or penalty weight (e.g., a 0.0multiplier). As such, the voice recognition terms having higher entityscores and having the greater number of matching entities can receive ahigher feasibility score.

In some implementations, the feasibility score can be a weighted averagescore of the identified entities within the voice recognition term. Forexample, in response to receiving a voice query that includes threeentities (e.g., entity name A, entity name B, and entity name C), thefeasibility score can be calculated based on the average of the entityscores for each of the identified entities. Again, to the extent thereare unrecognized terms within the voice recognition term, a suitablepenalty score or penalty weight can be applied to the feasibility score.

Referring back to FIG. 8, in response to determining the feasibilityscores for each of the voice recognition terms, the voice recognitionterms can be ranked based on the determined feasibility scores at 850.For example, as shown in FIG. 9, results table 900 includes thefeasibility scores in column 940 and the query interpretationapplication has ranked the voice recognition terms from highestfeasibility score to lowest feasibility score. As also shown in FIG. 9,the voice recognition term with the highest feasibility score is “watchfringe.”

At 860, the query interpretation application can perform a search with avoice recognition term selected based on the voice recognition termsranked by feasibility score. For example, as shown in FIG. 9, the queryinterpretation application can select the voice recognition term havingthe highest feasibility score (e.g., “watch fringe”). In anotherexample, the query interpretation application can select the voicerecognition term based on multiple criteria—e.g., a high feasibilityscore and a high score from a click log.

The query interpretation application can then cause the search resultsresponsive to the received voice query to be displayed to the user at870. For example, as shown in FIG. 9, in response to conducting anaction in the media playback device for the voice recognition term“watch fringe,” the query interpretation application provides an image950, a link 960, and/or other suitable information responsive to thevoice query. In another example, the query interpretation applicationcan execute the action command based on the selected voice recognitionterm on the computing device associated with the user that provided thevoice query.

In some implementations, the query interpretation application can allowthe user to select a language for receiving voice queries. For example,as shown in FIG. 9, the query interpretation application is configuredto receive voice queries in English. In another example, the queryinterpretation application can automatically detect the language forreceiving and interpreting voice queries based on the received voicequery.

FIG. 10 is a generalized schematic diagram of a system on which thequery interpretation application can be implemented in accordance withsome implementations of the disclosed subject matter. As illustrated,system 1000 can include one or more computing devices 1002, such as auser computing device for providing search queries and/or obtaining andplaying back media content items from various sources, a tabletcomputing device for transmitting user instructions to a televisiondevice, etc. For example, computing device 1002 can be implemented as apersonal computer, a tablet computing device, a personal digitalassistant (PDA), a portable email device, a multimedia terminal, amobile telephone, a gaming device, a set-top box, a television, a smarttelevision, etc.

In some implementations, computing device 1002 can include a storagedevice, such as a hard drive, a digital video recorder, a solid statestorage device, a gaming console, a removable storage device, or anyother suitable device for storing media content, entity tables, entityinformation, metadata relating to a particular search domain, etc.

In some implementations, computing device 1002 can include a secondscreen device. For example, the second screen device can display asearch interface for receiving search queries and, in response toreceiving search results responsive to a search query, can transmitplayback instructions for user-selected media content to a televisiondevice. In another example, a second screen device can present the userwith search and/or query interpretation preferences, where thepreferences are transmitted to a set-top box or a television device.

Computing devices 1002 can be local to each other or remote from eachother. For example, when one computing device 1002 is a television andanother computing device 1002 is a second screen device (e.g., a tabletcomputing device, a mobile telephone, etc.), the computing devices 1002may be located in the same room. Computing devices 1002 are connected byone or more communications links 1004 to a communications network 1006that is linked via a communications link 1008 to a server 1010.

System 1000 can include one or more servers 1010. Server 1010 can be anysuitable server for providing access to the query interpretationapplication, such as a processor, a computer, a data processing device,or a combination of such devices. For example, the query interpretationapplication can be distributed into multiple backend components andmultiple frontend components or interfaces. In a more particularexample, backend components, such as data distribution can be performedon one or more servers 1010. Similarly, the graphical user interfacesdisplayed by the query interpretation application, such as a searchinterface for retrieving media content or an interface for providingpreferences relating to entity-based query interpretation, can bedistributed by one or more servers 1010 to computing device 1002.

In some implementations, server 1010 can include any suitable server foraccessing metadata relating to a search domain, click logs, manuallycurated entity information, marketplace information, social mediainformation relating to entities, etc.

More particularly, for example, each of the computing devices 1002 andserver 1010 can be any of a general purpose device such as a computer ora special purpose device such as a client, a server, etc. Any of thesegeneral or special purpose devices can include any suitable componentssuch as a processor (which can be a microprocessor, digital signalprocessor, a controller, etc.), memory, communication interfaces,display controllers, input devices, etc. For example, computing device1002 can be implemented as a personal computer, a tablet computingdevice, a personal digital assistant (PDA), a portable email device, amultimedia terminal, a mobile telephone, a gaming device, a set-top box,a television, etc.

In some implementations, any suitable computer readable media can beused for storing instructions for performing the processes describedherein. For example, in some implementations, computer readable mediacan be transitory or non-transitory. For example, non-transitorycomputer readable media can include media such as magnetic media (suchas hard disks, floppy disks, etc.), optical media (such as compactdiscs, digital video discs, Blu-ray discs, etc.), semiconductor media(such as flash memory, electrically programmable read only memory(EPROM), electrically erasable programmable read only memory (EEPROM),etc.), any suitable media that is not fleeting or devoid of anysemblance of permanence during transmission, and/or any suitabletangible media. As another example, transitory computer readable mediacan include signals on networks, in wires, conductors, optical fibers,circuits, any suitable media that is fleeting and devoid of anysemblance of permanence during transmission, and/or any suitableintangible media.

Referring back to FIG. 10, communications network 1006 may be anysuitable computer network including the Internet, an intranet, awide-area network (“WAN”), a local-area network (“LAN”), a wirelessnetwork, a digital subscriber line (“DSL”) network, a frame relaynetwork, an asynchronous transfer mode (“ATM”) network, a virtualprivate network (“VPN”), or any combination of any of such networks.Communications links 1004 and 1008 may be any communications linkssuitable for communicating data between computing devices 1002 andserver 1010, such as network links, dial-up links, wireless links,hard-wired links, any other suitable communications links, or acombination of such links. Computing devices 1002 enable a user toaccess features of the application. Computing devices 1002 and server1010 may be located at any suitable location. In one implementation,computing devices 1002 and server 1010 may be located within anorganization. Alternatively, computing devices 1002 and server 1010 maybe distributed between multiple organizations.

Referring back to FIG. 10, the server and one of the computing devicesdepicted in FIG. 10 are illustrated in more detail in FIG. 11. Referringto FIG. 11, computing device 1002 may include processor 1102, display1104, input device 1106, and memory 1108, which may be interconnected.In a preferred implementation, memory 1108 contains a storage device forstoring a computer program for controlling processor 1102.

Processor 1102 uses the computer program to present on display 1104 thequery interpretation application and the data received throughcommunications link 1004 and commands and values transmitted by a userof computing device 1002. It should also be noted that data receivedthrough communications link 1004 or any other communications links maybe received from any suitable source. Input device 1106 may be acomputer keyboard, a mouse, a keypad, a cursor-controller, dial,switchbank, lever, a remote control, or any other suitable input deviceas would be used by a designer of input systems or process controlsystems. Alternatively, input device 1206 may be a finger or stylus usedon a touch screen display 1204. For receiving the voice queriesdescribed above, input device 1206 may be a microphone.

Server 1010 may include processor 1120, display 1122, input device 1124,and memory 1126, which may be interconnected. In a preferredimplementation, memory 1126 contains a storage device for storing datareceived through communications link 1008 or through other links, andalso receives commands and values transmitted by one or more users. Thestorage device further contains a server program for controllingprocessor 1120.

In some implementations, the application may include an applicationprogram interface (not shown), or alternatively, the application may beresident in the memory of computing device 1002 or server 1010. Inanother suitable implementation, the only distribution to computingdevice 1002 may be a graphical user interface (“GUI”) which allows auser to interact with the application resident at, for example, server1010.

In one particular implementation, the application may includeclient-side software, hardware, or both. For example, the applicationmay encompass one or more Web-pages or Web-page portions (e.g., via anysuitable encoding, such as HyperText Markup Language (“HTML”), DynamicHyperText Markup Language (“DHTML”), Extensible Markup Language (“XML”),JavaServer Pages (“JSP”), Active Server Pages (“ASP”), Cold Fusion, orany other suitable approaches).

Although the application is described herein as being implemented on auser computer and/or server, this is only illustrative. The applicationmay be implemented on any suitable platform (e.g., a personal computer(“PC”), a mainframe computer, a dumb terminal, a data display, a two-waypager, a wireless terminal, a portable telephone, a portable computer, apalmtop computer, an H/PC, an automobile PC, a laptop computer, acellular phone, a personal digital assistant (“PDA”), a combinedcellular phone and PDA, etc.) to provide such features.

Accordingly, methods, systems, and media for interpreting queries areprovided.

Although the disclosed subject matter has been described and illustratedin the foregoing illustrative implementations, it is understood that thepresent disclosure has been made only by way of example, and thatnumerous changes in the details of implementation of the disclosedsubject matter can be made without departing from the spirit and scopeof the disclosed subject matter. Features of the disclosedimplementations can be combined and rearranged in various ways.

What is claimed is:
 1. A method for interpreting queries, the methodcomprising: receiving, using a hardware processor, a search query thatincludes a plurality of search terms; determining, for at least aportion of the plurality of search terms, whether a search termcorresponds to an entity name, wherein the entity name is associatedwith a plurality of entity types; determining, for the search term andeach of the plurality of entity types, an entity score that indicatesrelatedness of the entity name to a corresponding entity type; removingat least one of the entity names based on the entity score to generate aremaining portion of entity names; and performing a search with theremaining portion of entity names, wherein each entity name in theremaining portion of entity names is searched corresponding to theassociated entity type.
 2. The method of claim 1, wherein the entityscore is based at least in part on popularity of the entity name in asearch domain.
 3. The method of claim 1, wherein the entity scoreassociated with the entity name is based at least in part on userfeedback information.
 4. The method of claim 1, further comprising;retrieving metadata corresponding to a search domain; extracting entitynames based on the retrieved metadata; determining, for each of theentity names, the entity type and the entity score associated with theentity name; and generating an entity table that includes, for each ofthe entity names, the entity name and the associated entity type andentity score.
 5. The method of claim 4, further comprising supplementingthe entity names in the generated entity table with curated entityinformation, wherein the curated entity information includes ignoredterms in the search query.
 6. The method of claim 4, further comprising:determining the search domain from a plurality of search domains basedon the received search query; and accessing the entity table from aplurality of entity tables based on the determined search domain.
 7. Themethod of claim 4, further comprising: storing the entity table;determining whether a predetermined amount of time has elapsed since theentity table was stored; in response to determining that thepredetermined amount of time has elapsed, retrieving updated metadatacorresponding to the search domain; and updating the entity table thatincludes entity names, entity types, and entity scores based on theupdated metadata.
 8. A system for interpreting queries, the systemcomprising: a storage device for storing entity information, wherein theentity information is derived from metadata associated with a searchdomain; and a processor that is configured to: receive a search querythat includes a plurality of search terms; determine, for at least aportion of the plurality of search terms, whether a search termcorresponds to an entity name, wherein the entity name is associatedwith a plurality of entity types; determine, for the search term andeach of the plurality of entity types, an entity score that indicatesrelatedness of the entity name to a corresponding entity type; remove atleast one of the entity names based on the entity score to generate aremaining portion of entity names; and perform a search with theremaining portion of entity names, wherein each entity name in theremaining portion of entity names is searched corresponding to theassociated entity type.
 9. The system of claim 8, wherein the entityscore is based at least in part on popularity of the entity name in thesearch domain.
 10. The system of claim 8, wherein the entity scoreassociated with the entity name is based at least in part on userfeedback information.
 11. The system of claim 8, wherein the processoris further configured to: retrieve metadata corresponding to the searchdomain; extract entity names based on the retrieved metadata; determine,for each of the entity names, the entity type and the entity scoreassociated with the entity name; and generate an entity table thatincludes, for each of the entity names, the entity name and theassociated entity type and entity score.
 12. The system of claim 11,wherein the processor is further configured to supplement the entitynames in the generated entity table with curated entity information,wherein the curated entity information includes ignored terms in thesearch query.
 13. The system of claim 11, wherein the processor isfurther configured to: determine the search domain from a plurality ofsearch domains based on the received search query; and access the entitytable from a plurality of entity tables based on the determined searchdomain.
 14. The system of claim 11, wherein the processor is furtherconfigured to: store the entity table in the storage device; determinewhether a predetermined amount of time has elapsed since the entitytable was stored; in response to determining that the predeterminedamount of time has elapsed, retrieve updated metadata corresponding tothe search domain; and update the entity table that includes entitynames, entity types, and entity scores based on the updated metadata.15. A non-transitory computer-readable medium containingcomputer-executable instructions that, when executed by a processor,cause the processor to perform a method for interpreting queries, themethod comprising: receiving a search query that includes a plurality ofsearch terms; determining, for at least a portion of the plurality ofsearch terms, whether a search term corresponds to an entity name,wherein the entity name is associated with a plurality of entity types;determining, for the search term and each of the plurality of entitytypes, an entity score that indicates relatedness of the entity name toa corresponding entity type; removing at least one of the entity namesbased on the entity score to generate a remaining portion of entitynames; and performing a search with the remaining portion of entitynames, wherein each entity name in the remaining portion of entity namesis searched corresponding to the associated entity type.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the entityscore is based at least in part on popularity of the entity name in asearch domain.
 17. The non-transitory computer-readable medium of claim15, wherein the entity score associated with the entity name is based atleast in part on user feedback information.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the method furthercomprises: retrieving metadata corresponding to a search domain;extracting entity names based on the retrieved metadata; determining,for each of the entity names, the entity type and the entity scoreassociated with the entity name; and generating an entity table thatincludes, for each of the entity names, the entity name and theassociated entity type and entity score.
 19. The non-transitorycomputer-readable medium of claim 18, wherein the method furthercomprises supplementing the entity names in the generated entity tablewith curated entity information, wherein the curated entity informationincludes ignored terms in the search query.
 20. The non-transitorycomputer-readable medium of claim 18, wherein the method furthercomprises: determining the search domain from a plurality of searchdomains based on the received search query; and accessing the entitytable from a plurality of entity tables based on the determined searchdomain.
 21. The non-transitory computer-readable medium of claim 18,wherein the method further comprises: storing the entity table;determining whether a predetermined amount of time has elapsed since theentity table was stored; in response to determining that thepredetermined amount of time has elapsed, retrieving updated metadatacorresponding to the search domain; and updating the entity table thatinclude entity names, entity types, and entity scores based on theupdated metadata.